System having automated route detection and app initiation

ABSTRACT

A system is disclosed for managing waste services by a service vehicle. The system may have a locating device configured to generate a location signal, a sensor configured to generate a service signal indicative of a waste service being performed, an input device, and a controller in communication with the locating device, the sensor, and the input device. The controller may be configured to make a determination that the service vehicle has made at least one service stop based on the location and service signals, and to make a comparison of characteristics of the at least one service stop with characteristics of at least one service stop of at least one known service route. Based on the comparison, the controller may be further configured to selectively transmit the recorded characteristics offboard the service vehicle.

TECHNICAL FIELD

The present disclosure relates generally to a system and an app (i.e., adownloadable self-contained software application) for use on a mobiledevice. More particularly, the present disclosure relates to a systemthat detects which route a service vehicle is following andautomatically calls up a corresponding graphical user interface within awaste management app for use by the vehicle operator during completionof the detected route.

BACKGROUND

Commercial and residential waste service providers typically dispatchservice vehicles to customer properties according to a predeterminedpickup schedule assigned to each vehicle. The pickup schedule for eachservice vehicle is often designed to provide waste services (e.g., toempty waste receptacles) within a particular geographical area and at aparticular frequency (e.g., once per week). After completion of eachwaste service (or periodically during completion of the route), thevehicle operator reports the completion to a back office, which updatesthe operator's pickup schedule and an account record for the customer.Customers that subscribe to these waste services are billed based on theaccount record. The operator then maneuvers the service vehicle to anext customer location for completion of additional waste services.

In some instances, it may be difficult to manage the pickup schedule foreach service vehicle. In particular, the pickup schedule can changefrequently and include new customer locations and/or locations havingcomplex service requirements. In these instances, it can be difficultfor the vehicle operator to determine which stops to make, the order ofthe stops, the timing of the stops, etc. It can also be difficult tofind the new locations, to determine travel routes to new locations, tomanage instructions associated with required services at each location,and to keep track of the completed services.

Waste management apps exist that, when called up by the vehicleoperator, can help the operator manage the assigned travel route. Forexample, the operator may be able to manually choose from a selectiondisplayed via the app which of a plurality of stored routes the operatorwould like to complete. The operator may then follow instructions fromthe app during completion of the chosen route, and provide feedback viathe app regarding completion of services at stops in the route.

While an improvement over previous methods, it may be difficult in someinstances to ensure that the vehicle operator calls up the available appat a beginning of an assigned route, that the operator correctly selectsthe right route for the given day and/or time of day, and/or that theoperator uses the app during completion of the route. In particular,some operators may not be properly trained how to use the app, whileother operators may be too occupied with other tasks to focus on use ofthe app.

The disclosed system and app are directed to overcoming one or more ofthe problems set forth above and/or other problems of the prior art.

SUMMARY

In one aspect, the present disclosure is directed to a system formanaging waste services by a service vehicle. The system may include alocating device configured to generate a location signal indicative of alocation of the service vehicle, a sensor configured to generate aservice signal indicative of a waste service being performed by theservice vehicle, an input device, and a controller in communication withthe locating device, the sensor, and the input device. The controllermay be configured to make a determination that the service vehicle hasmade at least one service stop based on the location and servicesignals, and to make a comparison of characteristics of the at least oneservice stop with characteristics of at least one service stop of atleast one known service route. Based on the comparison, the controllermay be further configured to selectively transmit the recordedcharacteristics offboard the service vehicle.

In another aspect, the present disclosure is directed to a method formanaging waste services by a service vehicle. The method may includegenerating a location signal indicative of a location of the servicevehicle, generating a service signal indicative of a waste service beingperformed by the service vehicle, and making a determination that theservice vehicle has made at least one service stop based on the locationand service signals. The method may also include making a comparison ofcharacteristics of the at least one service stop with characteristics ofat least one service stop of at least one known service route and, basedon the comparison, selectively displaying a graphical user interface onan input device inside of the service vehicle, showing informationassociated with the at least one known service route.

In yet another aspect, the present disclosure is directed to anon-transitory computer readable medium containing computer-executableprogramming instructions for managing waste services by a servicevehicle. The method may include generating a location signal indicativeof a location of the service vehicle, generating a service signalindicative of a waste service being performed by the service vehicle,and making a determination that the service vehicle has made at leastone service stop based on the location and service signals. The methodmay also include making a comparison of characteristics of the at leastone service stop with characteristics of at least one service stop of atleast one known service route and, based on the comparison, selectivelydisplaying a graphical user interface on an input device inside of theservice vehicle, showing information associated with the at least oneknown service route.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a perspective illustration of an exemplary disclosed wastemanagement environment;

FIG. 2 is a diagrammatic illustration of an exemplary disclosed systemthat may be used to manage the environment of FIG. 1;

FIG. 3 is an exemplary disclosed method that may be completed by thesystem of FIG. 2; and

FIG. 4 is a diagrammatic illustration of an exemplary disclosedgraphical user interface that may be used to access the system of FIG.2.

DETAILED DESCRIPTION

FIG. 1 illustrates an exemplary waste management environment(“environment”) 10, at which one or more vehicles 12 are providing wasteservices. Environment 10 may include a retail store, a factory, agovernment building, a residential address, or another location havingone or more receptacles 14 that require the service of vehicle(s) 12.The service may include, for example, the removal of waste materialsfrom inside of receptacle(s) 14, the replacement of receptacle(s) 14,and/or the placement of new or additional receptacles 14.

Vehicle 12 may take many different forms. In the example shown on theright in FIG. 1, vehicle 12 is a hydraulically actuated, front-loadingtype of vehicle. Specifically, vehicle 12 may include a bed 16 supportedby a plurality of wheels 18, a cab 20 located forward of bed 16, and alifting device 22 extending forward of cab 20. Lifting device 22 mayconsist of, among other things, one or more lift arms 24 configured toengage and/or grasp receptacle 14, and one or more actuators 26 poweredby pressurized oil to raise and tilt lift arms 24 (and receptacle 14) uppast cab 20 to a dump location over bed 16. After dumping of receptacle14, pressurized oil may be released from hydraulic actuator(s) 26 toallow lowering of lift arms 24 and receptacle 14 back to the ground infront of vehicle 12. In other examples, lifting device 22 may be locatedto pick up receptacles 14 from a side and/or a rear of vehicle 12. Inyet other examples, receptacles 14 may be manually lifted and dumpedinto bed 16. In any of these examples, bed 16 could be outfitted with acompactor (not shown) to compact the waste material after the materialis dumped into bed 16, and/or a door (not shown) configured to close anopening of bed 16 through which the waste material is dumped. Otherconfigurations may also be possible.

In the example shown on the left in FIG. 1, vehicle 12 is ahydraulically actuated flatbed or roll-off type of vehicle.Specifically, vehicle 12 may include a bed 16 supported by a pluralityof wheels 18, a cab 20 located forward of bed 16, and a lifting device22 extending rearward of cab 20. Lifting device 22 may consist of, amongother things, one or more actuators 26 powered by pressurized oil toraise and tilt receptacle 14 up onto bed 16 for transportation ofreceptacle 14 away from environment 10. After dumping of receptacle 14at a disposal site (or swapping a full receptacle 14 for an emptyreceptacle 14), receptacle 14 may be returned to environment 10 andlowered back to the ground behind vehicle 12 (e.g., by releasingpressurized oil from hydraulic actuator(s) 26).

As each vehicle 12 moves about environment 10, a satellite 28 or othertracking device may communicate with an onboard controller 30 (shownonly in FIG. 2) to monitor the movements of vehicle 12 and theassociated changes made to environment 10 (e.g., pickup, dumping,placement, etc.). As will be explained in more detail below, onboardcontroller 30, or a separate offboard controller (e.g., a controller 32located in a back office 34 or other service facility—shown only in FIG.2), may then manage future operations of vehicle 12 (and other similarvehicles 12) based on these movements and changes.

Both of onboard and offboard controllers 30, 32 may include means formonitoring, recording, storing, indexing, processing, communicating,and/or controlling other onboard and/or offboard devices. These meansmay include, for example, a memory, one or more data storage devices, acentral processing unit, or any other components that may be used to runthe disclosed application. Furthermore, although aspects of the presentdisclosure may be described generally as being stored in memory, oneskilled in the art will appreciate that these aspects can be stored onor read from different types of computer program products orcomputer-readable media such as computer chips and secondary storagedevices, including hard disks, floppy disks, optical media, CD-ROM, orother forms of RAM or ROM.

As shown in FIG. 2, onboard controller 30 may form a portion of a wastemanagement system (“system”) 36 that is configured to track, assist,and/or control movements of vehicle(s) 12 (shown only in FIG. 1). Inaddition to onboard controller 30, system 36 may also include a locatingdevice 38, and at least one of an input device 40 and a sensor 42mounted or otherwise located onboard each vehicle 12. In someembodiments, system 36 includes both manual input device 40 and one ormore sensors 42. In other embodiments, sensor 42 (and/or controller 30)may be internal to input device 40. Onboard controller 30 may be incommunication with each of these other components and/or with offboardcontroller 32 at back office 34 (e.g., via a communication device 44),and configured to determine, based on signals from these components andbased on other known information stored in memory, the location of eachvehicle 12 and characteristics and locations of receptacles 14 beingmoved by and/or in a vicinity of each vehicle 12.

Locating device 38 may be configured to generate location signalsindicative of a geographical position and/or orientation of vehicle 12relative to a local reference point, a coordinate system associated withenvironment 10, a coordinate system associated with Earth, or any othertype of 2-D or 3-D coordinate system. For example, locating device 38may embody an electronic receiver configured to communicate withsatellites 28 (referring to FIG. 1), or a local radio or lasertransmitting system used to determine a relative geographical locationof itself. Locating device 38 may receive and analyze high-frequency,low-power radio or laser signals from multiple locations to triangulatea relative 3-D geographical position and orientation. In someembodiments, locating device 38 may also be configured to determine alocation and/or orientation of a particular part of vehicle 12, forexample of lift arms 24 and/or actuators 26 (shown only in FIG. 1).Based on the location signals generated by locating device 38 and basedon known kinematics of vehicle 12, onboard controller 30 may be able todetermine in real time the position, heading, travel speed,acceleration, and orientation of vehicle 12, lift arms 24, and/oractuators 26. This information may then be used by onboard and/oroffboard controllers 30, 32 to update the locations and conditions ofvehicles 12 and/or receptacles 14 in an electronic map or database ofenvironment 10.

It is contemplated that locating device 38 may take another form, ifdesired. For example, locating device 38 could be or otherwise includean RFID reader configured to interact with an RFID tag located withinenvironment 10 (e.g., at a customer location, on receptacle 14, etc.),or another type of scanner configured to read another type of indicia(e.g., a barcode) within environment 10. Based on the reading of theRFID tag or other indicia, the location and/or orientation of vehicle 12may be linked to the known location of the RFID tag or other indiciawithin environment 10. It is also contemplated that a separate RFID orbarcode reader could be included in system 36, if desired.

Input device 40 may provide a way for an operator of vehicle 12 to inputinformation regarding observances made while traveling aroundenvironment 10. For example, the operator may be able to enter a typeand/or condition of waste observed at a particular location, an amountof waste in or around receptacle 14, a fill status of a particularreceptacle 14, a condition of receptacle 14, a location of receptacle14, and or other information about the receptacle and waste engaged by,loaded into, or otherwise processed by vehicle 12. The information maybe input in any number of ways, for example via a cab-mounted touchscreen interface, via one or more buttons, via a keyboard, via speechrecognition, via a mobile device (e.g., a smartphone or tablet) carriedby the operator, or in another manner known in the art. In someembodiments, the operator may also be able to respond to inquiriesreceived via input device 40, if desired. In addition to receivingmanual input from an operator, input device 40 may also be capable ofdisplaying information, for example the electronic map of environment10, instructions from back office 34, route information, payloadinformation (e.g., weight and/or volume), questions, etc.

In some embodiments, input device 40 may be configured to execute awaste management application. For example, when input device 40 is amobile device (for example a smartphone, tablet, or watch), theapplication can be a mobile app (“app”). An app is an abbreviated termfor a “software application”, which is downloadable to and executable bya mobile device (e.g., a laptop, a smartphone, a tablet, a dash-mounteddisplay, etc.). The disclosed waste management app can provide agraphical user interface (GUI) configured to display information about awaste service operation to the operator of vehicle 12; and that receivesinput from the operator used to configure acquisition of operationaldata by sensor(s) 42, to transmit the operational data to controllers30, 32, to receive and display information about a current operation(e.g., as monitored by sensor(s) 42), etc.

Sensors 42 may be configured to monitor parameters associated with thewaste material loaded into vehicle 12 and/or the associated receptacles14 being moved by vehicle 12 (e.g., moved by lift arms 24), and togenerate corresponding service signals indicative thereof. Each of thesesensors 42 may be any type of device known in the art, and locatedanywhere on or in vehicle 12. In one example, sensor 42 is a liftsensor, such as any one or more of a load cell, a force gauge, apressure sensor, a motion sensor, or another type of lift sensorassociated directly with lift arms 24, with actuator(s) 26, withreceptacle 14, and/or with a strut 46 supporting bed 16. In thisexample, the service signals generated by sensor(s) 42 may correspondwith strain on lift arms 24, with a force applied to lift arms 24 byactuator(s) 26, with a payload weight of bed 16, with a motion ofreceptacle 14, with a weight of waste contained inside receptacle 14,etc.

Alternatively, one or more sensors 42 may be associated with a powersource or drivetrain of vehicle 12, and configured to generate signalsindicative of an amount of power used to propel vehicle 12, to drive thehydraulics of actuators 26, to move the in-bed compactor, or to shut theassociated door. Other types of sensors 42 (e.g., cameras,spectrometers, IR sensors, RADAR sensors, LIDAR sensors, etc.) may alsobe utilized to determine characteristics (e.g., load profile, volume,and/or shape) of the waste material inside receptacles 14 or ofreceptacles 14 themselves. In yet further examples, sensor 42 could bean acoustic sensor (e.g., one or more microphones), an accelerometer, oranother similar type of sensor configured to detect engagementconditions and/or cycle completion of lift arms 24, the in-bedcompactor, the door, etc. during lifting, dumping, and/or shaking ofreceptacle 14. Other types of sensors 42 may alternatively oradditionally be utilized. Service signals generated by these sensors 42may be communicated to onboard and/or offboard controllers 30, 32, andthe corresponding processing unit may use the signals to determineconditions surrounding receptacles 14 (and/or the waste insidereceptacles 14) during servicing by vehicle 12. As described above, anyone or more of sensors(s) 42 may form an integral portion of inputdevice 40 (e.g., the smartphone or tablet carried by the operator) or bea standalone component in wired or wireless communication withcontrollers 30, 32 and/or input device 40, as desired.

Onboard controller 30 may be configured to manage communications betweenother onboard components and offboard controller 32 located at backoffice 34. For example, onboard controller 30 may receive locationsignals from locating device 38, informational signals from inputdevice(s) 40, and service signals from sensor(s) 42, and correlate thesignals, filter the signals, buffer the signals, record the signals, orotherwise condition the signals before directing the signals offboardvia communication device 44.

Communication device 44 may be configured to facilitate communicationbetween onboard controller 30 and offboard controller 32. Communicationdevice 44 may include hardware and/or software that enable the sendingand/or receiving of data messages through a communications link. Thecommunications link may include satellite, cellular, infrared, radio,and any other type of wireless communications. Alternatively, thecommunications link may include electrical, optical, or any other typeof wired communications, if desired. In one embodiment, onboardcontroller 30 may be omitted, and offboard controller 32 may communicatedirectly with locating device 38, input device(s) 40, and/or sensor(s)42 via communication device 44, if desired. Other means of communicationmay also be possible.

Onboard and/or offboard controllers 30, 32, based on the informationreceived from onboard vehicles 12 and also based on information receivedfrom other sources (e.g., from the Internet, from input received at backoffice 34, etc.), can be configured to execute instructions stored oncomputer readable medium to perform methods of waste management atenvironment 10. For example, onboard and/or offboard controllers 30, 32may be configured to monitor when vehicle 12 is nearing a servicelocation, when vehicle 12 has stopped, when vehicle 12 is servicingreceptacle 14 at the stop (i.e. when vehicle 12 has completed a servicestop), when vehicle 12 is filled with waste to a maximum capacity, etc.This monitoring may then be used to determine which one of a pluralityof different available routes a particular vehicle 12 is completing, andto record characteristics of the services performed during completion ofthe route. In addition, once the route being followed by the particularvehicle 12 has been determined, the disclosed app may be called into theforeground of or otherwise displayed on input device 40 and madeavailable for use by the operator. In some embodiments, the disclosedapp may already be in the foreground on input device 40 at a time whenthe route is automatically determined. In this situation, informationassociated with the determined route may then be displayed. Use of theapp may facilitate route adjustment and scheduling for vehicle 12,tracking of business costs and efficiencies, record keeping and billing,performance tracking and incentivizing, etc.

An exemplary process of waste service management that may be performedby onboard and/or offboard controllers 30, 32 is illustrated in FIG. 3and will be explained in more detail in the following section to furtherillustrate the disclosed concepts. In addition, FIG. 4 represents anexemplary Graphical User Interface (GUI) that may be shown in connectionwith the disclosed waste management app on any input device 40 for useby the operator of service vehicle 12 to access system 36. FIG. 4 willalso be discussed in greater detail below to further illustrate thedisclosed concepts.

INDUSTRIAL APPLICABILITY

The disclosed system, method, and app may be applicable to the wasteservice industry, where efficient management of waste services canaffect efficiency and profitability for a provider. The disclosedsystem, method, and app may give the provider a way to show individualvehicle operators the daily tasks assigned to a particular vehicle in anorganized manner. For example, the disclosed system, method, and app mayprovide a graphical user interface (GUI) allowing the operator to see aschedule of the daily tasks arranged in an order that reduces time,effort, unscheduled stops, and fuel, while also satisfying customerexpectations. The GUI provided by the disclosed system, method, and appmay also relay to the operator visual directions to customer locationsand service instructions for each location. In addition, the GUI mayprovide visual status indications associated with the service tasks, andallow the operator to provide feedback or other input regarding thetasks, the customer locations, the service vehicle, the schedule, etc.Finally, the disclosed system, method, and app may be used to trackservice operations, provide feedback to customers and service providers,and to update records associated with performed services. The disclosedapp may be automatically called up by the disclosed system into aforeground of input device 40 and made available for use by theoperator, without prior input from the operator being required.Operation of the disclosed system and app will now be described indetail with respect to FIGS. 3 and 4.

As seen in FIG. 3, the disclosed method may be implemented by onboardcontroller 30 and/or offboard controller 32 (e.g., by at least oneprocessing unit of at least one of these controllers), and begin withmonitoring of vehicle operations (Step 300). The vehicle operations mayinclude, for example, travel of vehicle 12 (e.g., tracking of location,heading, speed, and/or acceleration), a date of travel, a time of traveland/or stopping, a duration of stopping, use of lifting device 22 (e.g.,receptacle lifting, tilting, dumping, and associated force or weightchanges), use of the in-bed compactor (if available), use of the beddoor (if equipped), engagement and/or movement of receptacles 14, and/orother similar service related characteristics. These characteristics maybe monitored via locating device 38, sensor(s) 42, and/or input device40.

In some instances, the operations of vehicle 12 may be continuouslymonitored. In other instances, the operations may be monitored only at aparticular time of day (e.g., during a typical work shift), only duringparticular days of the week (e.g., only during the typical work week),only after vehicle 12 has been turned on, only when input device 40(e.g., the smartphone or tablet embodiment of input device 40) is placedwithin a threshold proximity to (e.g., inside of) vehicle 12, only wheninput device 40 is in communication with (e.g., has been paired with)the other components of system 36, etc. In the disclosed embodiment,initiation of service monitoring does not require input (e.g., login)from the operator. Instead, monitoring may be controlled via thedisclosed app, which may always be running in a background of inputdevice 40.

During monitoring of vehicular operations, the appropriate processingunit(s) may determine if any service stops have been completed andcharacteristics corresponding to the completed service stops (Step 310).The determination of completed service stops may be made based oncomparison of the monitored operations with one or more thresholdvalues. As described above, the operations may be monitored via locatingdevice 38 and/or sensors 44 and represented as location and/or servicesignals processed by onboard controller 30 and/or offboard controller32. For example, when a monitored travel speed of vehicle 12 falls belowa threshold value, it can be concluded that vehicle 12 has stopped. Andif a monitored movement of lifting device 22 corresponds with a minimummovement and/or force threshold, it can be concluded that a receptacle14 was lifted, tilted, and/or dumped into bed 16. When these actionsfollow each other sequentially and within a threshold period of time, itcan be concluded that service was performed at the stop.

The processing unit(s) may keep track of the completed service stops,the order of the stops, and the monitored characteristics correspondingto the stops, and compare this information to information stored inmemory to determine if a travel path currently being followed by servicevehicle 12 is a known service route (Step 320). In particular, onboardand/or offboard controllers 30, 32 may have stored in memory a pluralityof different and known service routes, one of which should be followedby the particular service vehicle 12. Each of these known service routesmay include a finite number of service stops arranged in a particularorder. And each of the service stops may have a corresponding location,and a set of characteristics corresponding to how the service should becompleted. For example, the characteristics may include a location ofthe service stop, a day and/or time of expected service, an expectedduration of the service, a number, type, size, and/or condition ofreceptacles 14 that should be emptied and/or onloaded by vehicle 12, atype of material expected to be in receptacles 14, an expected weight ofthe waste inside of receptacles 14, and/or an expected type of service(e.g., front lift and tilt, side tilt, rear manual lift, receptacleonload, etc.) to be performed with regard to receptacles 14. In someinstances, the characteristics may be at least partially dependent on adate of a last service, a day of the week of the current service, etc.

At step 320, after a number of service stops have been monitored, theappropriate processing unit(s) may compare the characteristics of themonitored service stops to stored characteristics of the same number ofservice stops listed in sequential order in each of the known routes todetermine if the travel path currently being followed by vehicle 12substantially matches one of the known service routes. For example,during a particular monitoring operation, a particular vehicle 12 may beobserved to make four different service stops. These stops couldinclude, for example, four different geographical locations visited insequential order, each stop occurring at a different time and/or takinga different amount of time to complete. At these four stops, threedifferent sizes of dumpsters (e.g., a 4 yd. dumpster, a 6 yd. dumpster,and then an 8 yd. dumpster) were lifted, tilted, and dumped into bed 16by lifting device 22, and one rubbish can was manually lifted and dumpedinto bed 16. The weights and/or types of waste material received fromeach of these receptacles 14 may be determined, and then the number,type, size, sequence, and/or corresponding waste material weights and/ortypes compared to the characteristics of four sequential stops withineach of the known service routes stored in memory. When the comparisonindicates a substantial match (e.g., within a threshold certainty),control may proceed to the next step. Otherwise, control may return toStep 300.

In one embodiment, following completion of Step 320 (i.e., after Step320:Y), the appropriate processing unit(s) may call the disclosed app tothe foreground within input device 40 and cause information to bedisplayed in association with the known route (Step 330). Theinformation may include, for example, all assigned stops within theknown route (e.g., a listing of scheduled stops provided in a particularorder). The information may also include a name of each stop, an addressof each stop, a map showing the location of each stop, a desired servicetime and/or duration for each stop, and instructions regardingparticular service tasks (e.g., pickup, empty, return, etc.) to beperformed at each stop. In addition, the information may include anindication as to which service stops have been completed, and whichservice stop is to be completed next. The disclosed processing unit(s)may continue to monitor operations of vehicle 12, and update accountrecords (e.g., customer records, provider records, vehicle records,operator records, etc.) with information from the previously monitoredoperations as well as from operations to be monitored in associationwith a remainder of the known route (Step 340).

In the same or another embodiment, following completion of step 320, theappropriate processing unit(s) may alternatively or additionally simplytrack and report completion of the current service route. That is, thedisclosed method may provide a way to monitor characteristics (e.g.,accuracy, timeliness, efficiency, productivity, volume, etc.) associatedwith operator and/or vehicle performance in association with the currentservice route, without the operator having to interact with the system.Information collected during completion of the service route may berecorded and reported to back office 34 during and/or after the service.

FIG. 4 shows an exemplary GUI 400, which may be used to facilitate themethod that is described above and shown in FIG. 3. GUI 400 may be shownon any input device 40 and, as can be seen in FIGS. 3 and 4, maycorrespond with steps 320 and 330 in the flowchart of FIG. 3. Inparticular, after completing step 320 and determining that the currenttravel path of vehicle 12 substantially matches one of the known serviceroutes stored in memory, GUI 400 may be called into the foreground ofinput device 40. In some instances, the matching of step 320 may beindicated within GUI 400, allowing the operator to override theprocessing unit's determination and pick a different one of the knownroutes.

In the example shown in FIG. 4, two stops are listed in the known route.The two stops include a first stop at John's Home and a second stop atBig J Coffee. It should be noted that each service route could includeany number of stops. John's Home is shown as being located at 3300Hillview Ave and has a scheduled service time of 8:00 am. Big J. Coffeeis shown as being located at 3500 Hillview Ave and has a later scheduledservice time of 9:00 am. The service to be completed at John's Home issimply to empty an existing receptacle 14 into bed 16 of vehicle 12;while the service to be completed at Big J Coffee is to pick up anexisting receptacle 14, take the receptacle 14 to a particular land fill(i.e., to Landfill A), and then to return the empty receptacle 14 backto Big J Coffee. Other service tasks could also or alternatively beassociated with each stop, as desired. The service at John's Home isshown as having been completed (e.g., with a checkmark).

The completion of service at a particular stop in an assigned route maybe confirmed manually and/or automatically, as desired. For example,upon completion of a particular service task at a particular location,the operator of vehicle 12 may provide manual input indicative of thecompletion to input device 40. This input could include, for example,pressing of a button, touching of a screen (e.g., touching the checkmarkarea shown in FIG. 4 at the left of “John's Home”), voicing an audiblecommand, etc.

After confirmation is received that waste services at a particular stopin the assigned route have been completed, the map shown in GUI 400 mayrepresent the relative location of vehicle 12, a next stop in the route,and/or directions from the current vehicle location to the next stop.That is, after completion of a service task at one stop, the disclosedapp may cause the map to be automatically updated and correspond withthe next stop. It is also contemplated that the operator may manuallyrequest the relative location associated with any particular stop to beshown in the map of GUI 400, if desired, regardless of the status of aparticular service task.

The interface illustrated in FIG. 4 is exemplary only and provided tohighlight certain aspects of the disclosed system. Other views andfunctionality are contemplated, as would be understood by one of skillin the art. It will be apparent to those skilled in the art that variousmodifications and variations can be made to the disclosed system. Otherembodiments will be apparent to those skilled in the art fromconsideration of the specification and practice of the disclosed system.It is intended that the specification and examples be considered asexemplary only, with a true scope being indicated by the followingclaims and their equivalents.

What is claimed is:
 1. A system for managing waste services by a servicevehicle, comprising: a locating device configured to generate a locationsignal indicative of a location of the service vehicle; a sensorconfigured to generate a service signal indicative of a waste servicebeing performed by the service vehicle; an input device; and acontroller in communication with the locating device, the sensor, andthe input device, the controller being configured to: make adetermination that the service vehicle has made at least one servicestop based on the location and service signals; make a comparison ofcharacteristics of the at least one service stop with characteristics ofat least one service stop of at least one known service route; based onthe comparison, selectively record the characteristics of all stops inthe at least one known service route; and transmit the recordedcharacteristics offboard the service vehicle.
 2. The system of claim 1,wherein: the at least one known service route includes a plurality ofknown service routes stored in memory; and the at least one service stopincludes a plurality of sequential service stops.
 3. The system of claim1, wherein the sensor is one of a lift sensor, a camera, and an acousticsensor.
 4. The system of claim 1, wherein: the input device is mobile;and the controller is configured to make the determination only when theinput device is within a threshold proximity of the service vehicle. 5.The system of claim 4, wherein the input device is one of a smartphoneor a tablet.
 6. The system of claim 1, wherein the controller is furtherconfigured to selectively call to a foreground of the input device agraphical user interface displaying information associated with the atleast one known service route based on the comparison.
 7. The system ofclaim 6, wherein the information associated with the at least one knownservice route includes a schedule of service stops to be completed bythe service vehicle.
 8. The system of claim 7, wherein the informationassociated with the at least one known service route further includes amap showing a location of the service vehicle relative to the servicestops in the schedule.
 9. They system of claim 7, wherein theinformation associated with the at least one service route furtherincludes instructions regarding each of the service stops in theschedule.
 10. The system of claim 1, wherein the controller is furtherconfigured to update account records associated with the at least oneservice stop based on the location signal, the service signal, and thecomparison.
 11. The system of claim 1, wherein the characteristics ofthe at least one service stop include at least one of a servicelocation, a date of service, a time of service, a duration of service, atype of service completed, a size of receptacle serviced, an amount ofwaste material received, and a type of waste material received.